Add version to meta.yaml #34
Conversation
|
Please any comments on this? |
| Updates to the minor version number are considered minor changes; | ||
| when a new minor version is released, bakeries will _overwrite the previous minor version_ of the feedstock's datasets. | ||
| Instead, the bakery should _always retain the latest major version_. | ||
| Updates that involve concatenation of new elements (e.g. extend the temporal range) are considered minor version updates. |
There was a problem hiding this comment.
This wording is confusing - didn't you just say that this would overwrite the dataset?
Similarly, retaining the major version: you mean that the latest minor version of each major version will be retained? i.e., that if 3.7 was followed by a 4.x series, then 3.7 will be kept for good, archival?
There was a problem hiding this comment.
didn't you just say that this would overwrite the dataset?
Yes I see how that is confusing. What I mean is that 3.6 ➡️ 3.7 will make 3.6 go away. We won't keep a separate copy of 3.6 around, since 3.7 supersedes it. But this may mean just renaming 3.6 to 3.7 and then appending to it. So I agree that "overwrite" is not necessarily the right word here.
if 3.7 was followed by a 4.x series, then 3.7 will be kept for good, archival?
Correct.
Co-authored-by: Charles Stern <[email protected]>
This is an update to the meta.yaml spec which makes a proposal about how to handle versioning of datasets.
Closes pangeo-forge/pangeo-forge-recipes#3
xref pangeo-forge/pangeo-forge-recipes#37, #29
please review and comment @pangeo-forge/dev-team, @davidbrochart.